Skip to content

Document NATS integration#266

Open
mavam wants to merge 6 commits intotopic/new-executorfrom
topic/nats
Open

Document NATS integration#266
mavam wants to merge 6 commits intotopic/new-executorfrom
topic/nats

Conversation

@mavam
Copy link
Copy Markdown
Member

@mavam mavam commented Apr 17, 2026

🔍 Problem

  • The new NATS JetStream operators need matching documentation beyond generated changelog notes.
  • Users need to find NATS from the integration index, message broker guides, and operator reference pages.

🛠️ Solution

  • Add from_nats and to_nats reference pages with syntax, authentication, TLS, metadata variables, and examples.
  • Add a NATS integration page and wire it into the Messaging sidebar and integration overview.
  • Update the collecting and routing guides where message brokers are discussed.

💬 Review

  • Check the NATS examples against the code PR operator names and argument names.
  • Check whether the NATS integration should get a dedicated diagram in a follow-up.
  • Verified locally with bun run lint.
🛠️ Code PR: tenzir/tenzir#6047
🎫 References TNZ-508

Add NATS operator reference pages, integration navigation, and message broker guide coverage for consuming from and publishing to NATS JetStream.
@github-actions github-actions Bot added guide How-to guides reference Reference documentation integration Integration documentation site Site infrastructure labels Apr 17, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 17, 2026

📦 Preview  ·  View →  ·  🟢 Live

Auto-updates on push

@mavam mavam changed the base branch from main to topic/new-executor April 17, 2026 04:57
mavam added 2 commits April 17, 2026 12:11
Clarify that NATS operators accept the standard Tenzir tls record but ignore tls.min_version because nats.c does not expose a matching setting.
Update the NATS reference and collecting guides for the parser-free source operator. Show payload parsing from the message field and metadata access through metadata_field.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 35def454e4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/content/docs/guides/collecting/read-from-message-brokers.mdx Outdated
Clarify that to_nats and to_kafka default to serializing events with this.print_ndjson() when message= is omitted.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 781a3e57ef

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/content/docs/reference/operators/to_kafka.mdx
Preserve NATS metadata in the collecting guide and reconcile Kafka/NATS default serialization examples across integration, guide, and reference pages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

guide How-to guides integration Integration documentation reference Reference documentation site Site infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant